fix(usage): handle missing Token Plan quota fields - #141

Hi @sonicg83, thank you for the contribution! The Token Plan usage view is a great addition, and the handling of omitted quota fields is well thought out. 🙏

I've pushed a follow-up commit (39a4881) on top of your branch to align it with a few repo conventions before merging. To summarize the changes:

Output format

• Replaced the mutually exclusive --json / --view flags with the repo-wide --output convention used by the other usage commands: the human-readable view is now the default, and --output json emits the four core fields. --dry-run also respects the selected format now.

Response parsing

• Relaxed readUsage to tolerant reading: each quota field is read independently, and any missing or non-numeric value is simply treated as absent (possibly unlimited) instead of throwing an "unexpected format" error. This matches our convention of not second-guessing well-formed 200 responses, and makes the "missing percentage → possibly unlimited" behavior unconditional.

Polish

• Translated the hardcoded Chinese "may be unlimited" messages to English to match the rest of the CLI output.
• Moved formatDateTime into shared.ts next to formatDate, introduced a QuotaWindow type, and simplified the line/progress-bar styling helpers.

Docs & tests

• Added the bl usage token-plan entry to the bailian-cli SKILL.md routing table and regenerated the reference docs.
• Restructured the e2e file to follow the two-block describe convention, and expanded the unit tests (7 → 12) to cover the JSON path with real data and the newly tolerated edge cases.

All checks pass (vp check clean, 12/12 unit tests, 5/5 e2e including real Console calls). Please take a look and let me know if anything doesn't match your intent — happy to adjust. Thanks again!